Content tagged with "engineering culture" (7)

Torvalds said 'talk is cheap, show me the code,' but now that machines can generate code, the person who can clearly articulate the problem is the one who matters.

After 14 years at Google, the lessons that stuck aren't about code, they're about navigating ambiguity, building trust, and the difference between being productive and being impactful.

Sometimes writing it yourself is the right call because the dependency you avoided understanding will eventually break, and then you'll have to understand it anyway under pressure.

The framework you pick matters far less than knowing it deeply; chasing rewrites rarely reaches the promised land, it just resets the treadmill.

Tools change; the method of systematically cornering the cause of a fault does not. A case for treating troubleshooting as a discipline you practice on purpose.

O'Reilly takes the long view, noting that every generation declared programming dead when the abstraction had only risen a level, and AI is the next rise.

A decade of reversed opinions from someone still in the trenches, where most of the certainties you pick up as a junior prove to be context-dependent.